<html xmlns="http://www.w3.org/1999/xhtml" xmlns:html="http://www.w3.org/1999/xhtml"><head><meta charset="UTF-8"/><style type="text/css">
      .optionalresource {
      }
      .optionalmethod1 {
      }
      .showoptionalresource {
        display: none;
      }
      body {
        font-family: sans-serif;
        font-size: 0.85em;
        margin: 2em 2em;
      }
      .methods {
        margin-left: 2em;
        margin-bottom: 2em;
      }
      .method {
        background-color: #eef;
        border: 1px solid #DDDDE6;
        padding: .5em;
        margin-bottom: 1em;
      /* width: 50em */
      }
      .methodNameTable {
        width: 100%;
        border: 0px;
        border-bottom: 2px solid white;
        font-size: 1.4em;
      }
      .methodNameTd {
        background-color: #eef;
      }
      h1 {
        font-size: 2m;
        margin-bottom: 0em;
      }
      h2 {
        border-bottom: 1px solid black;
        margin-top: 1.5em;
        margin-bottom: 0.5em;
        font-size: 1.5em;
      }
      h3 {
        color: #FF6633;
        font-size: 1.35em;
        margin-top: .5em;
        margin-bottom: 0em;
      }
      h5 {
        font-size: 1.2em;
        color: #99a;
        margin: 0.5em 0em 0.25em 0em;
      }
      h6 {
        color: #700000;
        font-size: 1em;
        margin: 1em 0em 0em 0em;
      }
      .h7 {
        margin-top: .75em;
        font-size: 1em;
        font-weight: bold;
        font-style: italic;
        color: blue;
      }
      .h8 {
        margin-top: .75em;
        font-size: 1em;
        font-weight: bold;
        font-style: italic;
        color: black;
      }
      tt {
        font-size: 1em;
      }
      table {
        margin-bottom: 0.5em;
        border: 1px solid #E0E0E0;
        width: 100%;
      }
      th {
        text-align: left;
        font-weight: normal;
        font-size: 1em;
        color: black;
        background-color: #DDDDE6;
        padding: 3px 6px;
        border: 1px solid #B1B1B8;
      }
      td {
        padding: 3px 6px;
        vertical-align: top;
        background-color: #F6F6FF;
        font-size: 0.85em;
      }
      p {
        margin-top: 1.2em;
        margin-bottom: 0em;
      }
      td.summary {
        background-color: white;
      }
      td.summarySeparator {
        padding: 1px;
      }</style><title>ABBI Pull API Documentation</title></head><body><button class="optionalresource" onclick="hideShowOptions('none')">Hide Optional Resources and
          Methods</button><button class="showoptionalresource" onclick="hideShowOptions('')">Show Optional Resources and
          Methods</button><script>
          function hideShowOptions(show)
          {
            var hide = show == "none" ? "" : "none";
            document.styleSheets[0].rules[0].style.display = show;
            document.styleSheets[0].rules[1].style.display = show;
            document.styleSheets[0].rules[2].style.display = hide;
          }
        </script><h1>ABBI Pull API Documentation</h1><br/><b>ABBI Pull API Documentation: </b><br/>
    <p>This document describes the Automate the Blue Button Initiative
      RESTful API enabling patients and caregivers access to patient
      documents. It has been generated via a <a href="wadl.xsl">transform</a> of
      the API <a href="ABBI.wadl">described</a> using <a href="http://www.w3.org/Submission/wadl/">WADL</a>.
      This document is divided into three sections:</p>
    <ol>
      <li><a href="#Summary">Summary</a>
        <p>Provides a summary of the API by resource and method.</p>
      </li>
      <li><a href="#Grammars">Grammars</a>
        <p>Provides the schemas that describe resources used in this
          API.</p></li>
      <li><a href="#Resources">Resources</a>
        <p>Describes each resource and the methods and parameters
          relevant to each resource</p>
      </li>
    </ol>
    <h5>Requirements</h5>
    <p> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
      NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
      in this document are to be interpreted as described in <a href="http://www.ietf.org/rfc/rfc2119.txt">RFC 2119</a>. </p>
    <p>An implementation is not compliant if it fails to satisfy one
      or more of the MUST or REQUIRED level requirements for the
      protocols it implements. An implementation that satisfies all the
      MUST or REQUIRED level and all the SHOULD level requirements for
      its protocols is said to be "unconditionally compliant"; one that
      satisfies all the MUST level requirements but not all the SHOULD
      level requirements for its protocols is said to be "conditionally
      compliant."</p>
    <h6>Server Conformance</h6>
    <p>Conformance requirements of servers appears following a heading
      labeled "Conformance" as in the following examples:</p>
  <br/><b>Conformance: </b><br/>REQUIRED<br/><b>Conformance: </b><br/>OPTIONAL
    <p>Conformance can be applied to resources, methods, parameters or
      parameter values. The table below indicates what it means to
      conform for each of the above. </p>
    <table border="1">
      <tr>
        <th>Component</th>
        <th>Server Conformance</th>
      </tr>
      <tr>
        <th>Resource</th><td>The server must support at least all
          required methods that operate on that resource</td>
      </tr>
      <tr>
        <th>Method</th><td>The server must demonstrate that
          successful completion of a request can be performed using that
          method.</td>
      </tr>
      <tr>
        <th>Parameter</th><td>The server must demonstrate that a
          successful completion of a request can be perfomed using one
          of the methods to which that parameter applies</td>
      </tr>
      <tr>
        <th>Parameter Value</th>
        <td>The server must demonstrate that a request can be
          performed where that parameter value is used.</td>
      </tr>
    </table>
    <h6>Client Conformance</h6>
    <p>Clients declaring conformance to this specification must
      demonstrate the ability to generate syntactically correct API
      calls using the resources, methods, parameters and parameter
      values in this specification. Clients need not demonstrate
      conformance to every resource, method, parameter or parameter
      value required of a server, but MUST demonstrate correct
      implementation of those API calls that are used, including use of
      all Required API parameters.</p>
  <h2 id="Summary">Summary</h2><table><tr><th style="width: 12em;">Resource<br/><span style="float:right">Method</span></th><th>Conformance</th><th>Description</th></tr><tbody class="optionalresource"><tr><td class="summary"><a href="#XdsEntry">/xdsentry</a></td><td class="summary">OPTIONAL</td><td class="summary">The XdsEntry resource provide metadata about each
          document available for a given patient. These resources are
          typically accessed through the search method. However, each
          XdsEntry resource has a URL and can be accessed
          individually.</td></tr><tr class="optionalmethod1"><td style="text-align: right"><a href="#d0e231">POST</a></td><td>OPTIONAL</td><td>Create a new XdsEntry resource.</td></tr></tbody><tbody class="resource"><tr><td class="summary"><a href="#d0e343">/xdsentry/latest</a></td><td class="summary">REQUIRED</td><td class="summary">This resource is simply an alias for the latest XdsEntry
            resource containing a clinical summary for this
            patient.</td></tr><tr class="method1"><td style="text-align: right"><a href="#d0e355">GET</a></td><td>REQUIRED</td><td>Retrieves (or constructs) the XdsEntry for the latest
              clinical summary available for a patient</td></tr></tbody><tbody class="resource"><tr><td class="summary"><a href="#d0e369">/xdsentry/search</a></td><td class="summary">REQUIRED</td><td class="summary">This resource produces an atom feed containing the
            XdsEntry resources matching the query parameters.</td></tr><tr class="method1"><td style="text-align: right"><a href="#d0e381">GET</a></td><td>REQUIRED</td><td>Retrieves an atom feed containing the set of XdsEntry
              resources matching the search criteria.</td></tr></tbody><tbody class="resource"><tr><td class="summary"><a href="#d0e801">/xdsentry/@{entryID}</a></td><td class="summary">REQUIRED</td><td class="summary">This is the XdsEntry resource specified by the entryId
            parameter.</td></tr><tr class="method1"><td style="text-align: right"><a href="#d0e820">GET</a></td><td>REQUIRED</td><td>Retrieve the specified XdsEntry resource.</td></tr><tr class="optionalmethod1"><td style="text-align: right"><a href="#d0e863">POST</a></td><td>OPTIONAL</td><td>Update the specified XdsEntry resource.</td></tr><tr class="optionalmethod1"><td style="text-align: right"><a href="#d0e918">DELETE</a></td><td>OPTIONAL</td><td>Delete the specified XdsEntry.</td></tr></tbody><tbody class="optionalresource"><tr><td class="summary"><a href="#document">/Document</a></td><td class="summary">OPTIONAL</td><td class="summary">This resource represents a document in a patient health
          record.</td></tr><tr class="optionalmethod1"><td style="text-align: right"><a href="#d0e1228">PUT</a></td><td>OPTIONAL</td><td>Stores the document.</td></tr></tbody><tbody class="resource"><tr><td class="summary"><a href="#d0e973">/Document/@{docId}</a></td><td class="summary">REQUIRED</td><td class="summary">This resource represents the specified document in the
            patient's health record.</td></tr><tr class="method1"><td style="text-align: right"><a href="#d0e994">GET</a></td><td>REQUIRED</td><td>Retrieves the specified document.</td></tr></tbody></table><p/><h2 id="Grammars">Grammars</h2><p><a href="file:/C:/MDHT_CDATools_1.1.0/workspace-consol/ABBI/WebContent/WEB-INF/xsd/atom.xsd">file:/C:/MDHT_CDATools_1.1.0/workspace-consol/ABBI/WebContent/WEB-INF/xsd/atom.xsd</a><br/><a href="file:/C:/MDHT_CDATools_1.1.0/workspace-consol/ABBI/WebContent/WEB-INF/xsd/fhir/xdsentry.xsd">file:/C:/MDHT_CDATools_1.1.0/workspace-consol/ABBI/WebContent/WEB-INF/xsd/fhir/xdsentry.xsd</a></p><h2 id="Resources">Resources</h2><p>This section describes the resources made accessible
        through ABBI</p><div class="optionalresource"><h3><a name="XdsEntry">/xdsentry</a></h3><p>The XdsEntry resource provide metadata about each
          document available for a given patient. These resources are
          typically accessed through the search method. However, each
          XdsEntry resource has a URL and can be accessed
          individually.</p>
      <br/><b>Conformance: </b><br/>OPTIONAL<h5>Methods</h5><div class="methods"><div class="method optionalmethod1"><table class="methodNameTable"><tr><td class="methodNameTd" style="font-weight: bold"><a name="d0e231">POST</a> /xdsentry</td><td class="methodNameTd" style="text-align: right"/></tr></table>
          <p>Create a new XdsEntry resource.</p>
          <dl><dt>NOTE:</dt>
            <dd>Some servers may also support PUT with the same
              semantics.</dd>
          </dl>
        <br/><b>Conformance: </b><br/><p>OPTIONAL</p><h6>request</h6><div style="margin-left: 2em"><div class="h7">header params</div><table><col style="width: 10em"/><col style="width: 15em"/><tr><td><span style="font-weight: bold">Authorization</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a><br/>(required)</td><td colspan="2">
          <p>Requires an OAuth 2.0 Token</p>
        </td></tr><tr><td rowspan="5"><span style="font-weight: bold">Content-Type</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a></td><td colspan="2"><p>Specifies the Content-Type of the POST
              body.</p></td></tr><tr><td><b>Values:</b><br/><tt><b>(Response Type)</b></tt></td><td><b>Description</b></td></tr><tr><td><tt>application/json<br/>(application/json)</tt></td><td>
                <p>The body represents an XdsEntry in application/json
                  format as defined <a href="http://www.hl7.org/implement/standards/fhir/fhir-book.htm#json">by HL7 here</a>.</p>
              </td></tr><tr><td><tt>text/fhir+xml<br/>(text/fhir+xml)</tt></td><td><p>The body is an XdsEntry element using the
                  text/fhir+xml format as defined <a href="http://www.hl7.org/implement/standards/fhir/fhir-book.htm#xdsentry">by HL7 here</a>.</p>
              </td></tr><tr><td><tt>text/xml<br/>(text/fhir+xml)</tt></td><td>
                <p>A synonym for text/fhir+xml.</p>
              </td></tr></table><p/><div class="h7">query params</div><table><col style="width: 10em"/><col style="width: 15em"/><tr><td rowspan="7"><span style="font-weight: bold">_format</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a></td><td colspan="2">
          <p>The _format parameter is provided to enable applications
            without control over HTTP Headers to specify the format of
            the resource.</p>
          <p>It indicates the format used to represent the XdsEntry
            resource. Overrides the Accept header if present in GET and
            search operations, and the Content-Type header in PUT or
            POST operations.</p>
        </td></tr><tr><td><b>Values:</b><br/><tt><b>(Response Type)</b></tt></td><td><b>Description</b></td></tr><tr><td><tt>application/json<br/>(application/json)</tt></td><td>
            <p>The resource will be returned in application/json
              format as defined <a href="http://www.hl7.org/implement/standards/fhir/fhir-book.htm#json">by HL7 here</a>.</p>
          </td></tr><tr><td><tt>json<br/>(application/json)</tt></td><td>
            <p>A synonym for application/json.</p>
          </td></tr><tr><td><tt>text/fhir+xml<br/>(text/fhir+xml)</tt></td><td>
            <p>The resource appears as an XdsEntry element using the
              text/fhir+xml format as defined <a href="http://www.hl7.org/implement/standards/fhir/fhir-book.htm#xdsentry">by HL7 here</a>.</p>
          </td></tr><tr><td><tt>text/xml<br/>(text/fhir+xml)</tt></td><td>
            <p>A synonym for text/fhir+xml.</p>
          </td></tr><tr><td><tt>xml<br/>(text/fhir+xml)</tt></td><td>
            <p>A synonym for text/fhir+xml.</p>
          </td></tr></table><p/></div><h6>responses</h6><div style="margin-left: 2em"><div class="h8">201</div><br/><b>Created: </b><br/><p>The resource has been created. The
              body contains a copy of the new resource in the specified
              mime type.</p><div style="margin-left: 2em"><div class="h7">headers</div><table><col style="width: 10em"/><col style="width: 15em"/><tr><td><span style="font-weight: bold">Location</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#uri">uri</a></td><td colspan="2"><p>A version-aware Location header which contains the
                new location and id of the created resource.</p><br/><b>Example: </b><br/><pre>/xdsentry/@{new-id}/history/@{new-vid}</pre></td></tr></table></div><div class="h8">400</div><br/><b>Bad Request: </b><br/><p>The resource could not be
              parsed.</p><div class="h8">404</div><br/><b>Not Found: </b><br/><p>Resource type not supported or not
              a FHIR end point.</p><div class="h8">490</div><br/><b>Talk to the Hand: </b><br/><p> the proposed resource
              violated server business rules. This should be accompanied
              by an Issue resource providing additional
            detail</p><div style="margin-left: 2em"><div class="h7">representations</div><table><tr><td style="font-weight: bold">text/fhir+xml</td><td colspan="2"><p>A description of the issue. See <a href="http://www.hl7.org/implement/standards/fhir/fhir-book.htm#issuereport">IssueReport</a> for details on the
              content.</p></td></tr></table></div></div></div></div></div><div class="resource"><h3><a name="d0e343">/xdsentry/latest</a></h3>
          <p>This resource is simply an alias for the latest XdsEntry
            resource containing a clinical summary for this
            patient.</p>
        <br/><b>Conformance: </b><br/><p>REQUIRED</p><h5>Methods</h5><div class="methods"><div class="method method1"><table class="methodNameTable"><tr><td class="methodNameTd" style="font-weight: bold"><a name="d0e355">GET</a> /xdsentry/latest</td><td class="methodNameTd" style="text-align: right"/></tr></table>
            <p>Retrieves (or constructs) the XdsEntry for the latest
              clinical summary available for a patient</p>
          <br/><b>Conformance: </b><br/><p>REQUIRED</p><h6>request</h6><div style="margin-left: 2em"><div class="h7">header params</div><table><col style="width: 10em"/><col style="width: 15em"/><tr><td><span style="font-weight: bold">Authorization</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a><br/>(required)</td><td colspan="2">
          <p>Requires an OAuth 2.0 Token</p>
        </td></tr></table><p/><div class="h7">query params</div><table><col style="width: 10em"/><col style="width: 15em"/><tr><td rowspan="7"><span style="font-weight: bold">_format</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a></td><td colspan="2">
          <p>The _format parameter is provided to enable applications
            without control over HTTP Headers to specify the format of
            the resource.</p>
          <p>It indicates the format used to represent the XdsEntry
            resource. Overrides the Accept header if present in GET and
            search operations, and the Content-Type header in PUT or
            POST operations.</p>
        </td></tr><tr><td><b>Values:</b><br/><tt><b>(Response Type)</b></tt></td><td><b>Description</b></td></tr><tr><td><tt>application/json<br/>(application/json)</tt></td><td>
            <p>The resource will be returned in application/json
              format as defined <a href="http://www.hl7.org/implement/standards/fhir/fhir-book.htm#json">by HL7 here</a>.</p>
          </td></tr><tr><td><tt>json<br/>(application/json)</tt></td><td>
            <p>A synonym for application/json.</p>
          </td></tr><tr><td><tt>text/fhir+xml<br/>(text/fhir+xml)</tt></td><td>
            <p>The resource appears as an XdsEntry element using the
              text/fhir+xml format as defined <a href="http://www.hl7.org/implement/standards/fhir/fhir-book.htm#xdsentry">by HL7 here</a>.</p>
          </td></tr><tr><td><tt>text/xml<br/>(text/fhir+xml)</tt></td><td>
            <p>A synonym for text/fhir+xml.</p>
          </td></tr><tr><td><tt>xml<br/>(text/fhir+xml)</tt></td><td>
            <p>A synonym for text/fhir+xml.</p>
          </td></tr></table><p/></div><h6>responses</h6><div style="margin-left: 2em"> unspecified </div></div></div></div><div class="resource"><h3><a name="d0e369">/xdsentry/search</a></h3>
          <p>This resource produces an atom feed containing the
            XdsEntry resources matching the query parameters.</p>
        <br/><b>Conformance: </b><br/><p>REQUIRED</p><h5>Methods</h5><div class="methods"><div class="method method1"><table class="methodNameTable"><tr><td class="methodNameTd" style="font-weight: bold"><a name="d0e381">GET</a> /xdsentry/search</td><td class="methodNameTd" style="text-align: right"/></tr></table>
            <p>Retrieves an atom feed containing the set of XdsEntry
              resources matching the search criteria.</p>
            <p>Several of the query parameters can be repeated. To
              repeat a parameter, specify it multiple times as separate
              query parameters. For example, to request content that is
              available in either xml or html format, you would use
              mimeType=xml&amp;mimeType=html in the query
              parameter.</p>
          <br/><b>Conformance: </b><br/><p>REQUIRED</p><h6>request</h6><div style="margin-left: 2em"><div class="h7">header params</div><table><col style="width: 10em"/><col style="width: 15em"/><tr><td><span style="font-weight: bold">Authorization</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a><br/>(required)</td><td colspan="2">
          <p>Requires an OAuth 2.0 Token</p>
        </td></tr></table><p/><div class="h7">query params</div><table><col style="width: 10em"/><col style="width: 15em"/><tr><td rowspan="7"><span style="font-weight: bold">_format</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a></td><td colspan="2">
          <p>The _format parameter is provided to enable applications
            without control over HTTP Headers to specify the format of
            the resource.</p>
          <p>It indicates the format used to represent the XdsEntry
            resource. Overrides the Accept header if present in GET and
            search operations, and the Content-Type header in PUT or
            POST operations.</p>
        </td></tr><tr><td><b>Values:</b><br/><tt><b>(Response Type)</b></tt></td><td><b>Description</b></td></tr><tr><td><tt>application/json<br/>(application/json)</tt></td><td>
            <p>The resource will be returned in application/json
              format as defined <a href="http://www.hl7.org/implement/standards/fhir/fhir-book.htm#json">by HL7 here</a>.</p>
          </td></tr><tr><td><tt>json<br/>(application/json)</tt></td><td>
            <p>A synonym for application/json.</p>
          </td></tr><tr><td><tt>text/fhir+xml<br/>(text/fhir+xml)</tt></td><td>
            <p>The resource appears as an XdsEntry element using the
              text/fhir+xml format as defined <a href="http://www.hl7.org/implement/standards/fhir/fhir-book.htm#xdsentry">by HL7 here</a>.</p>
          </td></tr><tr><td><tt>text/xml<br/>(text/fhir+xml)</tt></td><td>
            <p>A synonym for text/fhir+xml.</p>
          </td></tr><tr><td><tt>xml<br/>(text/fhir+xml)</tt></td><td>
            <p>A synonym for text/fhir+xml.</p>
          </td></tr><tr><td rowspan="13"><span style="font-weight: bold">mimeType</span><br/><a href="http://hl7.org/fhir#code-simple">code-simple</a><br/>(repeating)</td><td colspan="2"><p>Various mime types and/or information models can
                  be used to represent different kinds of content,
                  including summary notes, discharge notes, operative
                  notes, et cetera. This parameter filters the responses
                  to ensure that only specified notes are included. The
                  following values are supported: </p></td></tr><tr><td><b>Values:</b></td><td><b>Description</b></td></tr><tr><td><tt>text/xml</tt></td><td><p> Documents supporting the text/xml mime type.
                    These include XML formats such as <a href="http://www.hl7.org">HL7</a>'s <a href="http://www.hl7.org/implement/standards/product_brief.cfm?product_id=7">CDA</a> (including <a href="http://www.hl7.org/implement/standards/product_brief.cfm?product_id=6">CCD</a> or <a href="http://www.hl7.org/implement/standards/product_brief.cfm?product_id=258">CCDA</a>) or <a href="http://www.astm.org/">ASTM</a>'s <a href="http://www.astm.org/Standards/E2369.htm">CCR</a>. </p></td></tr><tr><td><tt>xml</tt></td><td><p> An alias for text/xml. </p></td></tr><tr><td><tt>text/html</tt></td><td><p> Documents rendered in the text/html mime
                    type. This includes any HTML suitable for rendering,
                    including <a href="http://www.w3.org/TR/html4/">HTML 4</a>, <a href="http://www.w3.org/TR/html/">XHTML</a> or
                      <a href="http://www.w3.org/TR/html5/">HTML
                      5</a>. </p></td></tr><tr><td><tt>html</tt></td><td><p> An alias for text/html. </p></td></tr><tr><td><tt>text/plain</tt></td><td><p> A document rendered as a simple text file,
                    such as might be produced using the original Blue
                    Button interface. </p></td></tr><tr><td><tt>text</tt></td><td><p> An alias for text/plain. </p></td></tr><tr><td><tt>plain</tt></td><td><p> Another alias for text/plain. </p></td></tr><tr><td><tt>application/pdf</tt></td><td><p> A document rendered using the <a href="http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/PDF32000_2008.pdf">Portable Document Format</a>, including <a href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=38920">PDF/A</a>. </p></td></tr><tr><td><tt>pdf</tt></td><td><p>An alias for application/pdf.</p></td></tr><tr><td><tt>application/json</tt></td><td><p> A document rendered in the format specified
                    in <a href="http://www.irt.org/rfc/rfc4627.htm">RFC 4627</a>. </p></td></tr><tr><td><tt>json</tt></td><td><p>An alias for application/json.</p></td></tr><tr><td rowspan="5"><span style="font-weight: bold">format</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#code-simple">code-simple</a><br/>(repeating)</td><td colspan="2"><p>The text/xml mime type can represent information
                  using a variety of different schemas representing
                  different information models. The purpose of this
                  parameter is to allow users to request information
                  conforming to a specific information models.
                </p></td></tr><tr><td><b>Values:</b></td><td><b>Description</b></td></tr><tr><td><tt>CCR</tt></td><td><p> Content formatted using the ASTM <a href="http://www.astm.org/Standards/E2369.htm">CCR</a> Standard </p></td></tr><tr><td><tt>CCD</tt></td><td><p> Content formatted using the HL7 CDA Standard
                    that conforms to the <a href="http://www.hl7.org/implement/standards/product_brief.cfm?product_id=6">Continuity of Care Document Release 1.0</a>
                  </p></td></tr><tr><td><tt>CCDA</tt></td><td><p> Content formatted using the HL7 CDA Standard
                    that conforms to the <a href="http://www.hl7.org/implement/standards/product_brief.cfm?product_id=258">Consolidated CDA Specification (including CCD
                      1.1)</a>
                  </p></td></tr><tr><td rowspan="11"><span style="font-weight: bold">class</span><br/><a href="http://hl7.org/fhir#code-simple">code-simple</a><br/>(repeating)</td><td colspan="2"><p>Various mime types and/or information models can
                  be used to represent different kinds of content,
                  including summary notes, discharge notes, operative
                  notes, et cetera. This parameter filters the responses
                  to ensure that only specified notes are
                  included.</p>
              <br/><b>Example: </b><br/>
                <pre>class=HandP&amp;class=Consult</pre>
              </td></tr><tr><td><b>Values:</b></td><td><b>Description</b></td></tr><tr><td><tt>Summaries</tt></td><td><p>Summary records using CCD (1.0 or 1.1) and/or
                    CCR</p></td></tr><tr><td><tt>HandP</tt></td><td><p>History and Physical Notes</p></td></tr><tr><td><tt>Consult</tt></td><td><p>Consultation Notes</p></td></tr><tr><td><tt>Discharge</tt></td><td><p>Discharge Summaries</p></td></tr><tr><td><tt>Operative</tt></td><td><p>Operative Notes</p></td></tr><tr><td><tt>Procedure</tt></td><td><p>Procedure Notes</p></td></tr><tr><td><tt>Progess</tt></td><td><p>Progress Notes</p></td></tr><tr><td><tt>Imaging</tt></td><td><p>Imaging Reports</p></td></tr><tr><td><tt>Lab</tt></td><td><p>Laboratory Studies</p></td></tr><tr><td><span style="font-weight: bold">service.start-after</span><br/><a href="http://hl7.org/fhir#dateTime-simple">dateTime-simple</a></td><td colspan="2"><p>Filters entries starting on or after the
                  specified time.</p>
                <h4 id="timezone">Time Zone</h4>
                <p>If time is specified, the time zone may be
                  specified. If time is not specified, time zone is not
                  permitted. When time zone is not specified, behavior
                  with respect to time zone is not specified. The server
                  may assume local time, local time of the querying
                  system, or some other fixed time zone.</p><br/><b>Examples: </b><br/>
                <p>To specify services starting after 6:00am on
                  January 1, 2012 in the Eastern Time
                    Zone:<pre>/xdsentry/search?service.start-after=2012-01-01T06:00-05:00</pre></p>
                <p>To specify services starting after 6:00am on
                  January 1, 2012 with no time zone
                    <pre>/xdsentry/search?service.start-after=2012-01-01T06:00</pre></p>
              </td></tr><tr><td><span style="font-weight: bold">service.start-before</span><br/><a href="http://hl7.org/fhir#dateTime-simple">dateTime-simple</a></td><td colspan="2">
                <p>Filters entries starting before the specified time.
                  See <a href="timezone">notes on time zone</a>
                  above.</p>
              <br/><b>Examples: </b><br/>
                <p>To specify all services starting on January 1, 2012
                    <pre>/xdsentry/search?service.start-after=2012-01-01&amp;service.start-before=2012-01-02</pre>
                </p>
                <p>To specify all services starting before January 1,
                  2012
                    <pre>/xdsentry/search?service.start-before=2012-01-01</pre>
                </p>
              </td></tr><tr><td><span style="font-weight: bold">service.stop-after</span><br/><a href="http://hl7.org/fhir#dateTime-simple">dateTime-simple</a></td><td colspan="2"><p>Filters entries stopping on or after the
                  specified time. See <a href="timezone">notes on time
                    zone</a> above.</p><br/><b>Examples: </b><br/>
                <p>To specify only services that occured on on the
                  date of January 1, 2012
                    <pre>/xdsentry/search?service.start-before=2012-01-02&amp;service.stop-after=2012-01-01</pre>
                </p>
                <p>To specify only services that occured between the
                  hours of noon and 1pm on the date of January 1, 2012
                    <pre>/xdsentry/search?service.start-before=2012-01-01T13:00:00&amp;service.stop-after=2012-01-01T12:00:00</pre>
                </p>
              </td></tr><tr><td><span style="font-weight: bold">service.stop-before</span><br/><a href="http://hl7.org/fhir#dateTime-simple">dateTime-simple</a></td><td colspan="2"><p>Filters entries stopping before the specified
                  time</p>. See <a href="timezone">notes on time
                  zone</a> above.</td></tr><tr><td><span style="font-weight: bold">created-after</span><br/><a href="http://hl7.org/fhir#dateTime-simple">dateTime-simple</a></td><td colspan="2"><p>Filters entries created on or after the
                  specified time</p>. See <a href="timezone">notes
                  on time zone</a> above.</td></tr><tr><td><span style="font-weight: bold">created-before</span><br/><a href="http://hl7.org/fhir#dateTime-simple">dateTime-simple</a></td><td colspan="2"><p>Filters entries created before the specified
                  time</p>. See <a href="timezone">notes on time
                  zone</a> above.</td></tr><tr><td><span style="font-weight: bold">_count</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#positiveInteger">positiveInteger</a><br/>default: <tt>1</tt></td><td colspan="2"><p>Starting offset of the first resource to return
                  in the search set.</p>
                <p>The _count and _n parameters allow the content of
                  the atom feed (or it’s JSON equivalent) to be
                  paginated. The value of _n specifies the ordinal
                  position of the first record to be returned. The
                  _count parameter specifies the maximum number of
                  records desired. The server must honor the value in
                  the n parameter, or return a 501 Not Implemented error
                  if it does not support pagination. It should honor the
                  count parameter. </p>
                <dl><dt>NOTE:</dt><dd>Pagination may return
                    inconsistent results between calls when new content
                    is being made available.</dd></dl>
              <br/><b>Example: </b><br/>
                <p>To retrieve 10 resources:
                    <pre>/xdsentry/search?_count=10</pre>
                </p>
              </td></tr><tr><td><span style="font-weight: bold">_n</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#positiveInteger">positiveInteger</a></td><td colspan="2"><p>Number of return resources requested. The server
                  is not bound to conform</p><br/><b>Example: </b><br/><p>To return the most recent
                  entry.</p><br/><b>Ordering of Responses: </b><br/>
                <p>In order for pagination to work, responses must
                  have a defined order. Responses are ordered by by
                  document creation time (from most to least recent),
                  and then by document identifier to ensure consistent
                  order. When results are being aggregated across
                  multiple systems (e.g., through a federated query),
                  the overall results and ordering may vary between
                  calls. Pagination is defined as a convenience
                  mechanism, but cannot guarantee that the same results
                  will be provided between calls.</p>
              <br/><b>Example: </b><br/>
                <p>To retrieve starting at the 11
                  resource: <pre>/xdsentry/search?_n=11</pre>
                </p>
              </td></tr></table><p/></div><h6>responses</h6><div style="margin-left: 2em"> unspecified </div></div></div></div><div class="resource"><h3><a name="d0e801">/xdsentry/@{entryID}</a></h3>
          <p>This is the XdsEntry resource specified by the entryId
            parameter.</p>
        <br/><b>Conformance: </b><br/><p>REQUIRED</p><h5>Methods</h5><div class="methods"><div class="method method1"><table class="methodNameTable"><tr><td class="methodNameTd" style="font-weight: bold"><a name="d0e820">GET</a> /xdsentry/@{entryID}</td><td class="methodNameTd" style="text-align: right"/></tr></table>
            <p>Retrieve the specified XdsEntry resource.</p>
          <br/><b>Conformance: </b><br/><p>REQUIRED</p><h6>request</h6><div style="margin-left: 2em"><div class="h7">template params</div><table><col style="width: 10em"/><col style="width: 15em"/><tr><td><span style="font-weight: bold">entryId</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a><br/>(required)</td><td colspan="2"><p>Specifies the XdsEntry resource to operate on by its
              unique identifier</p></td></tr></table><p/><div class="h7">header params</div><table><col style="width: 10em"/><col style="width: 15em"/><tr><td><span style="font-weight: bold">Authorization</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a><br/>(required)</td><td colspan="2">
          <p>Requires an OAuth 2.0 Token</p>
        </td></tr><tr><td rowspan="5"><span style="font-weight: bold">Accept</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a></td><td colspan="2">Indicates the format to return the resource in.</td></tr><tr><td><b>Values:</b><br/><tt><b>(Response Type)</b></tt></td><td><b>Description</b></td></tr><tr><td><tt>application/json<br/>(application/json)</tt></td><td><p>See documentation above for the format
                    parameter</p></td></tr><tr><td><tt>text/xml<br/>(text/fhir+xml)</tt></td><td><p>See documentation above for the format
                    parameter</p></td></tr><tr><td><tt>text/fhir+xml<br/>(text/fhir+xml)</tt></td><td><p>See documentation above for the format
                    parameter</p></td></tr></table><p/><div class="h7">query params</div><table><col style="width: 10em"/><col style="width: 15em"/><tr><td rowspan="7"><span style="font-weight: bold">_format</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a></td><td colspan="2">
          <p>The _format parameter is provided to enable applications
            without control over HTTP Headers to specify the format of
            the resource.</p>
          <p>It indicates the format used to represent the XdsEntry
            resource. Overrides the Accept header if present in GET and
            search operations, and the Content-Type header in PUT or
            POST operations.</p>
        </td></tr><tr><td><b>Values:</b><br/><tt><b>(Response Type)</b></tt></td><td><b>Description</b></td></tr><tr><td><tt>application/json<br/>(application/json)</tt></td><td>
            <p>The resource will be returned in application/json
              format as defined <a href="http://www.hl7.org/implement/standards/fhir/fhir-book.htm#json">by HL7 here</a>.</p>
          </td></tr><tr><td><tt>json<br/>(application/json)</tt></td><td>
            <p>A synonym for application/json.</p>
          </td></tr><tr><td><tt>text/fhir+xml<br/>(text/fhir+xml)</tt></td><td>
            <p>The resource appears as an XdsEntry element using the
              text/fhir+xml format as defined <a href="http://www.hl7.org/implement/standards/fhir/fhir-book.htm#xdsentry">by HL7 here</a>.</p>
          </td></tr><tr><td><tt>text/xml<br/>(text/fhir+xml)</tt></td><td>
            <p>A synonym for text/fhir+xml.</p>
          </td></tr><tr><td><tt>xml<br/>(text/fhir+xml)</tt></td><td>
            <p>A synonym for text/fhir+xml.</p>
          </td></tr></table><p/></div><h6>responses</h6><div style="margin-left: 2em"> unspecified </div></div><div class="method optionalmethod1"><table class="methodNameTable"><tr><td class="methodNameTd" style="font-weight: bold"><a name="d0e863">POST</a> /xdsentry/@{entryID}</td><td class="methodNameTd" style="text-align: right"/></tr></table>
            <p>Update the specified XdsEntry resource.</p>
          <br/><b>Conformance: </b><br/><p>OPTIONAL</p><h6>request</h6><div style="margin-left: 2em"><div class="h7">template params</div><table><col style="width: 10em"/><col style="width: 15em"/><tr><td><span style="font-weight: bold">entryId</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a><br/>(required)</td><td colspan="2"><p>Specifies the XdsEntry resource to operate on by its
              unique identifier</p></td></tr></table><p/><div class="h7">header params</div><table><col style="width: 10em"/><col style="width: 15em"/><tr><td><span style="font-weight: bold">Authorization</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a><br/>(required)</td><td colspan="2">
          <p>Requires an OAuth 2.0 Token</p>
        </td></tr><tr><td rowspan="5"><span style="font-weight: bold">Content-Type</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a></td><td colspan="2"><p>Specifies the Content-Type of the POST
                  body.</p></td></tr><tr><td><b>Values:</b><br/><tt><b>(Response Type)</b></tt></td><td><b>Description</b></td></tr><tr><td><tt>application/json<br/>(application/json)</tt></td><td>
                  <p>The body represents an XdsEntry in
                    application/json format as defined <a href="http://www.hl7.org/implement/standards/fhir/fhir-book.htm#json">by HL7 here</a>.</p>
                </td></tr><tr><td><tt>text/fhir+xml<br/>(text/fhir+xml)</tt></td><td><p>The body is an XdsEntry element using the
                    text/fhir+xml format as defined <a href="http://www.hl7.org/implement/standards/fhir/fhir-book.htm#xdsentry">by HL7 here</a>.</p>
                </td></tr><tr><td><tt>text/xml<br/>(text/fhir+xml)</tt></td><td>
                  <p>A synonym for text/fhir+xml.</p>
                </td></tr></table><p/><div class="h7">query params</div><table><col style="width: 10em"/><col style="width: 15em"/><tr><td rowspan="7"><span style="font-weight: bold">_format</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a></td><td colspan="2">
          <p>The _format parameter is provided to enable applications
            without control over HTTP Headers to specify the format of
            the resource.</p>
          <p>It indicates the format used to represent the XdsEntry
            resource. Overrides the Accept header if present in GET and
            search operations, and the Content-Type header in PUT or
            POST operations.</p>
        </td></tr><tr><td><b>Values:</b><br/><tt><b>(Response Type)</b></tt></td><td><b>Description</b></td></tr><tr><td><tt>application/json<br/>(application/json)</tt></td><td>
            <p>The resource will be returned in application/json
              format as defined <a href="http://www.hl7.org/implement/standards/fhir/fhir-book.htm#json">by HL7 here</a>.</p>
          </td></tr><tr><td><tt>json<br/>(application/json)</tt></td><td>
            <p>A synonym for application/json.</p>
          </td></tr><tr><td><tt>text/fhir+xml<br/>(text/fhir+xml)</tt></td><td>
            <p>The resource appears as an XdsEntry element using the
              text/fhir+xml format as defined <a href="http://www.hl7.org/implement/standards/fhir/fhir-book.htm#xdsentry">by HL7 here</a>.</p>
          </td></tr><tr><td><tt>text/xml<br/>(text/fhir+xml)</tt></td><td>
            <p>A synonym for text/fhir+xml.</p>
          </td></tr><tr><td><tt>xml<br/>(text/fhir+xml)</tt></td><td>
            <p>A synonym for text/fhir+xml.</p>
          </td></tr></table><p/></div><h6>responses</h6><div style="margin-left: 2em"> unspecified </div></div><div class="method optionalmethod1"><table class="methodNameTable"><tr><td class="methodNameTd" style="font-weight: bold"><a name="d0e918">DELETE</a> /xdsentry/@{entryID}</td><td class="methodNameTd" style="text-align: right"/></tr></table>
            <p>Delete the specified XdsEntry.</p>
          <br/><b>Conformance: </b><br/><p>OPTIONAL</p><h6>request</h6><div style="margin-left: 2em"><div class="h7">template params</div><table><col style="width: 10em"/><col style="width: 15em"/><tr><td><span style="font-weight: bold">entryId</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a><br/>(required)</td><td colspan="2"><p>Specifies the XdsEntry resource to operate on by its
              unique identifier</p></td></tr></table><p/><div class="h7">header params</div><table><col style="width: 10em"/><col style="width: 15em"/><tr><td><span style="font-weight: bold">Authorization</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a><br/>(required)</td><td colspan="2">
          <p>Requires an OAuth 2.0 Token</p>
        </td></tr></table><p/><div class="h7">query params</div><table><col style="width: 10em"/><col style="width: 15em"/><tr><td rowspan="7"><span style="font-weight: bold">_format</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a></td><td colspan="2">
          <p>The _format parameter is provided to enable applications
            without control over HTTP Headers to specify the format of
            the resource.</p>
          <p>It indicates the format used to represent the XdsEntry
            resource. Overrides the Accept header if present in GET and
            search operations, and the Content-Type header in PUT or
            POST operations.</p>
        </td></tr><tr><td><b>Values:</b><br/><tt><b>(Response Type)</b></tt></td><td><b>Description</b></td></tr><tr><td><tt>application/json<br/>(application/json)</tt></td><td>
            <p>The resource will be returned in application/json
              format as defined <a href="http://www.hl7.org/implement/standards/fhir/fhir-book.htm#json">by HL7 here</a>.</p>
          </td></tr><tr><td><tt>json<br/>(application/json)</tt></td><td>
            <p>A synonym for application/json.</p>
          </td></tr><tr><td><tt>text/fhir+xml<br/>(text/fhir+xml)</tt></td><td>
            <p>The resource appears as an XdsEntry element using the
              text/fhir+xml format as defined <a href="http://www.hl7.org/implement/standards/fhir/fhir-book.htm#xdsentry">by HL7 here</a>.</p>
          </td></tr><tr><td><tt>text/xml<br/>(text/fhir+xml)</tt></td><td>
            <p>A synonym for text/fhir+xml.</p>
          </td></tr><tr><td><tt>xml<br/>(text/fhir+xml)</tt></td><td>
            <p>A synonym for text/fhir+xml.</p>
          </td></tr></table><p/></div><h6>responses</h6><div style="margin-left: 2em"><div class="h8">204</div><br/><b>No Content: </b><br/><p>Returned if the deletion is
                successful. Subsequent attempts to access the resource
                will result in an error (e.g., 404 Not Found or 410
                Gone).</p><div class="h8">405</div><br/><b>Method Not Allowed: </b><br/><p>Returned if resource
                deletion is not supported by the server.</p><div class="h8">409</div><br/><b>Conflict: </b><br/><p>Returned if the server refuses to
                delete a resource because of reasons specific to that
                resource, such as referential integrity.</p></div></div></div></div><div class="optionalresource"><h3><a name="document">/Document</a></h3>
        <p>This resource represents a document in a patient health
          record.</p>
      <br/><b>Conformance: </b><br/><p>OPTIONAL</p><h5>Methods</h5><div class="methods"><div class="method optionalmethod1"><table class="methodNameTable"><tr><td class="methodNameTd" style="font-weight: bold"><a name="d0e1228">PUT</a> /Document</td><td class="methodNameTd" style="text-align: right"/></tr></table>
          <p>Stores the document.</p>
        <br/><b>Conformance: </b><br/><p>OPTIONAL</p><h6>request</h6><div style="margin-left: 2em"><div class="h7">header params</div><table><col style="width: 10em"/><col style="width: 15em"/><tr><td><span style="font-weight: bold">Authorization</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a><br/>(required)</td><td colspan="2"><p>Requires an OAuth 2.0 Token</p></td></tr><tr><td><span style="font-weight: bold">Content-Type</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a><br/>(required)</td><td colspan="2">
              <p>The mimeType and charset of the content.</p>
            </td></tr></table><p/><div class="h7">query params</div><table><col style="width: 10em"/><col style="width: 15em"/><tr><td><span style="font-weight: bold">_format</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a></td></tr></table><p/></div><h6>responses</h6><div style="margin-left: 2em"><div class="h8">201</div><br/><b>Created: </b><br/><p>The document was
            created.</p><div style="margin-left: 2em"><div class="h7">headers</div><table><col style="width: 10em"/><col style="width: 15em"/><tr><td><span style="font-weight: bold">Location</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#uri">uri</a><br/>(required)</td><td colspan="2"><p>A version-aware Location header which contains the
                new location and id of the created document.</p><br/><b>Example: </b><br/><pre>/Document/@{new-id}/history/@{new-vid}</pre></td></tr></table></div><div class="h8">400</div><br/><b>Bad Request: </b><br/><p>The document could not be
              parsed.</p><div class="h8">404</div><br/><b>Not Found: </b><br/><p>Resource type not supported or not
              a FHIR end point.</p></div></div></div></div><div class="resource"><h3><a name="d0e973">/Document/@{docId}</a></h3>
          <p>This resource represents the specified document in the
            patient's health record.</p>
        <br/><b>Conformance: </b><br/><p>REQUIRED</p><h5>Methods</h5><div class="methods"><div class="method method1"><table class="methodNameTable"><tr><td class="methodNameTd" style="font-weight: bold"><a name="d0e994">GET</a> /Document/@{docId}</td><td class="methodNameTd" style="text-align: right"/></tr></table>
            <p>Retrieves the specified document.</p>
          <br/><b>Conformance: </b><br/><p>REQUIRED</p><h6>request</h6><div style="margin-left: 2em"><div class="h7">template params</div><table><col style="width: 10em"/><col style="width: 15em"/><tr><td><span style="font-weight: bold">docId</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a><br/>(required)</td><td colspan="2">
            <p>The unique identifier for the document.</p>
          </td></tr></table><p/><div class="h7">header params</div><table><col style="width: 10em"/><col style="width: 15em"/><tr><td><span style="font-weight: bold">Authorization</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a><br/>(required)</td><td colspan="2"><p>Requires an OAuth 2.0 Token</p></td></tr><tr><td rowspan="8"><span style="font-weight: bold">Accept</span><br/><a href="http://www.w3.org/TR/xmlschema-2/#string">string</a></td><td colspan="2"><p>Servers MAY use the Accept header to identify
                  which rendering of the document to return. Some
                  servers ignore the accept header and return the
                  document in its original mime type.</p></td></tr><tr><td><b>Values:</b><br/><tt><b>(Response Type)</b></tt></td><td><b>Description</b></td></tr><tr><td><tt>text/xml<br/>(text/xml)</tt></td><td><p> Documents supporting the text/xml mime type.
                    These include XML formats such as <a href="http://www.hl7.org">HL7</a>'s <a href="http://www.hl7.org/implement/standards/product_brief.cfm?product_id=7">CDA</a> (including <a href="http://www.hl7.org/implement/standards/product_brief.cfm?product_id=6">CCD</a> or <a href="http://www.hl7.org/implement/standards/product_brief.cfm?product_id=258">CCDA</a>) or <a href="http://www.astm.org/">ASTM</a>'s <a href="http://www.astm.org/Standards/E2369.htm">CCR</a>. </p></td></tr><tr><td><tt>text/html<br/>(text/html)</tt></td><td><p> Documents will be rendered in the text/html
                    mime type. This includes any HTML suitable for
                    rendering, including <a href="http://www.w3.org/TR/html4/">HTML 4</a>,
                      <a href="http://www.w3.org/TR/html/">XHTML</a>
                    or <a href="http://www.w3.org/TR/html5/">HTML
                      5</a>. </p></td></tr><tr><td><tt>text/plain<br/>(text/plain)</tt></td><td><p> A document rendered as a simple text file,
                    such as might be produced using the original Blue
                    Button interface. </p></td></tr><tr><td><tt>application/pdf<br/>(application/pdf)</tt></td><td><p> A document rendered using the <a href="http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/PDF32000_2008.pdf">Portable Document Format</a>, including <a href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=38920">PDF/A</a>. </p>
                </td></tr><tr><td><tt>application/json<br/>(application/json)</tt></td><td><p> A document rendered in the format specified
                    in <a href="http://www.irt.org/rfc/rfc4627.htm">RFC 4627</a>. </p></td></tr><tr><td><tt>*/*<br/>(*/*)</tt></td><td><p>Other formats may be supported by the
                    server.</p></td></tr></table><p/><div class="h7">query params</div><table><col style="width: 10em"/><col style="width: 15em"/><tr><td rowspan="14"><span style="font-weight: bold">mimeType</span><br/><a href="http://hl7.org/fhir#code-simple">code-simple</a><br/>(repeating)</td><td colspan="2"><p>Documents can be rendered in various mime types
                  to represent their content. This parameter identifies
                  the the mime types that may be used for document
                  rendering. If more than one mime type is specified,
                  the server will send the format providing the most
                  machine-readable information content. XML and JSON are
                  preferred over HTML, PDF or plain text. HTML and PDF
                  are preferred over plain text. </p>
                <p>When present, this parameter overrides the Accept
                  header.</p>
              </td></tr><tr><td><b>Values:</b><br/><tt><b>(Response Type)</b></tt></td><td><b>Description</b></td></tr><tr><td><tt>text/xml<br/>(text/xml)</tt></td><td><p> Documents supporting the text/xml mime type.
                    These include XML formats such as <a href="http://www.hl7.org">HL7</a>'s <a href="http://www.hl7.org/implement/standards/product_brief.cfm?product_id=7">CDA</a> (including <a href="http://www.hl7.org/implement/standards/product_brief.cfm?product_id=6">CCD</a> or <a href="http://www.hl7.org/implement/standards/product_brief.cfm?product_id=258">CCDA</a>) or <a href="http://www.astm.org/">ASTM</a>'s <a href="http://www.astm.org/Standards/E2369.htm">CCR</a>. </p></td></tr><tr><td><tt>xml<br/>(text/xml)</tt></td><td><p> An alias for text/xml.</p></td></tr><tr><td><tt>text/html<br/>(text/html)</tt></td><td><p> Documents will be rendered in the text/html
                    mime type. This includes any HTML suitable for
                    rendering, including <a href="http://www.w3.org/TR/html4/">HTML 4</a>,
                      <a href="http://www.w3.org/TR/html/">XHTML</a>
                    or <a href="http://www.w3.org/TR/html5/">HTML
                      5</a>. </p></td></tr><tr><td><tt>html<br/>(text/html)</tt></td><td><p> An alias for text/html. </p></td></tr><tr><td><tt>text/plain<br/>(text/plain)</tt></td><td><p> A document rendered as a simple text file,
                    such as might be produced using the original Blue
                    Button interface. </p></td></tr><tr><td><tt>text<br/>(text/plain)</tt></td><td><p> An alias for text/plain. </p></td></tr><tr><td><tt>plain<br/>(text/plain)</tt></td><td><p> Another alias for text/plain. </p></td></tr><tr><td><tt>application/pdf<br/>(application/pdf)</tt></td><td><p> A document rendered using the <a href="http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/PDF32000_2008.pdf">Portable Document Format</a>, including <a href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=38920">PDF/A</a>. </p></td></tr><tr><td><tt>pdf<br/>(application/pdf)</tt></td><td><p>An alias for application/pdf.</p></td></tr><tr><td><tt>application/json<br/>(application/pdf)</tt></td><td><p> A document rendered in the format specified
                    in <a href="http://www.irt.org/rfc/rfc4627.htm">RFC 4627</a>. </p></td></tr><tr><td><tt>json<br/>(application/json)</tt></td><td><p>An alias for application/json.</p></td></tr><tr><td><tt>*/*<br/>(*/*)</tt></td><td><p>Other formats and aliases may be supported by
                    the server.</p></td></tr></table><p/></div><h6>responses</h6><div style="margin-left: 2em"> unspecified </div></div></div></div></body></html>